Skip to content

docs(kermt): fix install and Dockerfile paths in the vendored KERMT README#6

Open
evasnow1992 wants to merge 2 commits into
NVIDIA-BioNeMo:mainfrom
evasnow1992:evax/kermt-readme-vdr-fixes
Open

docs(kermt): fix install and Dockerfile paths in the vendored KERMT README#6
evasnow1992 wants to merge 2 commits into
NVIDIA-BioNeMo:mainfrom
evasnow1992:evax/kermt-readme-vdr-fixes

Conversation

@evasnow1992

Copy link
Copy Markdown
Collaborator

Summary

Two path references in the vendored KERMT skills README (open-models-skills/kermt/README.md) did not resolve in this repo's layout:

  1. The "Installing the skills" snippet (and the Codex / Nemotron pointers) referenced agent/skills/kermt-*/, which does not exist here — following it installs no skills.
  2. The "Container-first" section linked ../Dockerfile "at the repo root", which does not resolve in this repo, so the image-build reference dangles.

Root cause: this README is vendored from the KERMT model repo's agent/ directory (recorded in .skillsource.json), and vendoring relocates the files without the agent/ prefix. Paths written relative to the KERMT repo root
therefore no longer resolve once the file lands at open-models-skills/kermt/README.md.

Changes

  • Install snippet + Codex/Nemotron pointers: agent/skills/... -> skills/..., expressed relative to the README's own directory (matching the file's other skills/ links) so they resolve both in the KERMT repo and in this vendored copy.
  • Container-first: replaced the unresolved ../Dockerfile link with $KERMT_REPO/Dockerfile — the path kermt-setup actually builds the image from. No broken link, correct in either location.
  • "Running the tests": qualified the helper invocations with $KERMT_REPO/. The inner pytest agent/tests/... paths are intentionally left repo-relative

Relationship to the KERMT source

These are open-model skills whose canonical source is the KERMT model repo (agent/). The equivalent fix is being made upstream in agent/README.md using layout-independent paths (README-relative for install references, $KERMT_REPO/... for repo-root references), so re-syncing the vendored copy from source preserves it. No repo-specific path hardcoding was introduced here, to keep this copy aligned with the upstream README.

Bring the KERMT open-model skill bundle up to date with the KERMT repo main
branch (NVIDIA-BioNeMo/KERMT @ 85f255f):

- Adds the released-model download path: scripts/fetch_released_model.py +
  config/released_model.json, and the --pretrained-release / default-to-
  nvidia/NV-KERMT-70M-v2 flow in the finetune / embed / continue-pretrain
  SKILL.md files.
- Refreshes all 8 SKILL.md, all runner/validator scripts, and the unit tests.
- Regenerates the installable plugin SKILL.md copies.
- Updates .skillsource.json (resolved_sha + files list).
- Preserves the toolkit's Apache-2.0 OR CC-BY-4.0 dual-license identifier on
  all synced files (SPDX headers + SKILL.md frontmatter); KERMT ships
  Apache-2.0 only.
- Keeps the toolkit metadata convention: drops KERMT's owner: frontmatter
  field (no personal owner email in the public repo).

.skillsource.json was hand-updated (the autogenerate sync tool is not in the
public repo); a future generator run should reproduce it.

Signed-off-by: Eva Xue <evax@nvidia.com>
Mirror of the upstream KERMT agent/README.md fix. The vendored copy drops the
`agent/` prefix during vendoring, which left install snippets pointing at a
non-existent `agent/skills/` and a dangling `../Dockerfile` link. Use
README-relative `skills/` paths and reference `$KERMT_REPO/Dockerfile` (the
image the skills actually build from), so the instructions work from this
bundle. Test-helper invocations qualified with `$KERMT_REPO/`.

Stopgap until the README is re-vendored from KERMT source by the autogenerate
build step.

Signed-off-by: Eva Xue <evax@nvidia.com>
@evasnow1992 evasnow1992 requested review from kyle-gion and trvachov July 6, 2026 20:56
@evasnow1992

Copy link
Copy Markdown
Collaborator Author

This PR currently includes the changes in #3 . That PR will need to be merged first before this one can be merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant